After you create a vault, you can later view and edit the options that you set during creation as well as others. You might want to do this to:
To view or edit a vault's properties:
(missing or bad snippet)
Option | Description |
---|---|
Name |
Internal name of the vault. Read-only. |
Display name |
Name of the vault as seen by users. Read-only. For information on renaming a vault, see Renaming a vault. |
Engine |
Name of the database engine for the current vault. Read-only. |
SQL Server |
Name of the instance of SQL Server where this vault's database is hosted. Available only if the vault was created with the SQL Server engine. If the instance is hosted on the same computer as the Meridian application server, this option is blank. Read-only. |
Account |
SQL Server account name used to connect to the vault database on the server specified in SQL Server. Available only if the vault was created with the SQL Server engine. For information about setting this option and its password, see Configuring the SQL Server account used by Meridian. |
Database path |
Path of vault database files. Read-only. For information about moving a vault, see About moving a vault. |
Index path |
Path where the index files created by the database engine are stored. Available only if the vault was created with the SQL Server engine. For guidelines on estimating the space required and location options, see Understanding document storage space requirements. |
Log path |
Path where the transaction log files created by the database engine are stored. Available only if the vault was created with the SQL Server engine. For guidelines on estimating the space required and location options, see Understanding document storage space requirements. |
Content path |
Path of vault content files. Read-only. For information about moving a vault, see About moving a vault. |
Backup path |
Path where the backup files created by the SQL Server and Oracle database engines are stored. For guidelines on estimating the space required and location options, see Understanding document storage space requirements. |
Maintain history on Main area |
Retains all revisions of documents that are changed within the Main area of the vault. Otherwise, only the latest revision will reside in the vault. This option uses more disk space. To remove unused revisions, they can be archived as described in Archiving documents or removed as described in Removing vault history. For information on not using history for mechanical industry applications, see the BlueCielo Meridian Enterprise User's Guide. |
Hide documents from users with insufficient privileges |
Controls the visibility of documents depending on the user's security privileges. Enabling this option will have a negative effect on server performance when displaying folder contents, evaluating security, and searches. |
Force clients to access documents from Local Workspace |
Controls the use of Local Workspace. For more information, see About Local Workspace. |
Click the Advanced Features tab to view or edit the vault's additional options described in the following table.
Option | Description |
---|---|
Audit table connection string |
Connection to an external database where vault audit trail data is stored by the Meridian FDA Module. Type a valid connection string to an existing OLE DB database or click the hyperlink and build one with the Data Link Properties dialog that appears. Enabling this option requires a Meridian FDA Module server license. For more information, see the BlueCielo Meridian FDA Module Configuration Guide. |
Notifications table connection string |
Connection to an existing external database where document subscription data is stored. Type a valid connection string to an existing OLE DB database or click the hyperlink and build one with the Data Link Properties dialog that appears. For information about creating this database, see Creating a subscriptions database. For information about creating a connection string, see Data Connections, Data Sources, and Connection Strings (SSRS) on Microsoft TechNet. For information about configuring notification definitions to use this database, see the BlueCielo Meridian Enterprise Configuration Guide. Note This table is not used to store notification message information, only subscription data. The design assumption is that most customers will use both notifications and subscriptions. If you only want to use notifications, you must still enter a text value for this option. The value does not need to be a valid connection string. Notifications are enabled only if this option is not empty. |
Enable Advanced Project Workflow Module |
Enables the features of the Meridian Advanced Project Workflow Module. Enabling this option requires a Meridian Advanced Project Workflow Server license and Meridian Asset Management Module client extension licenses. |
Enable Asset Management Module |
Enables the integrated features of the Meridian Asset Management Module. Use of this module requires Meridian Asset Management Module client extension licenses. |
Enable BlueCielo Publisher extension |
Enables the integrated features of BlueCielo Publisher. Requires appropriate BlueCielo Publisherlicenses to be registered. |
Related concepts
Understanding the Meridian Enterprise Administrator
Related tasks